Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added report issue vikunja integration #273

Merged
merged 6 commits into from
Aug 11, 2024
Merged

Conversation

jabelone
Copy link
Member

@jabelone jabelone commented Aug 7, 2024

No description provided.

Copy link

github-actions bot commented Aug 7, 2024

Created image with name membermatters/membermatters:untrusted-pr-feature-vikunja-integration.

Copy link

github-actions bot commented Aug 7, 2024

Created image with name membermatters/membermatters:untrusted-pr-feature-vikunja-integration.

Copy link

github-actions bot commented Aug 7, 2024

Created image with name membermatters/membermatters:untrusted-pr-feature-vikunja-integration.

@proffalken
Copy link
Contributor

@jabelone - does this remove the Trello configuration? That's something we're currently relying on, so if we need to migrate to another system it would be better to know now than when this gets merged!

@jabelone
Copy link
Member Author

jabelone commented Aug 7, 2024

@proffalken I haven’t tested it in a while but it should still work after this refactor - you might just have to re-enable it as the feature flag has changed for consistency. Technically the trello integration is deprecated - in the sense that it’s not actively supported/maintained but it’s still there. I will un-deprecate it if you are using it as it’s a fairly simple integration to maintain, just didn’t think anyone was! We stopped using it when they killed the free tier (iirc tiny project limits) and never really looked at it since.

At BMS we’re using Vikunja because it’s open source / self hosted and supports oauth with MM. We’ve decided that all our digital platforms have to support oauth with MM because it causes too much of a burden on members and the committee if it doesn’t. It’s not quite as nice as trello, but is fine once you get familiar with the quirks.

I’m also adding a post to discord option too! That will make it in before I merge this. Our volunteer capacity is expanding quite rapidly and we’re trying to move things from “that’s Jaimyn’s (my) problem” to “that’s everyone’s problem” and part of that is just more visibility into things. That’s why I’ve been focused on things like adding member visible statistics, better observability and integrations like this.

@proffalken
Copy link
Contributor

@jabelone - your comment on Trello not being free made me go back and look at the pricing structure again.

It seems that the reason we've been able to continue on the free tier is because only a handful of folks are creating tickets and I'd not thought about hooking it up to the SSO capabilities of MM before.

I've taken a look at Vikunja and it looks like a perfectly acceptable replacement for our usage of Trello so I'm happy for you to leave the Trello stuff as deprecated and I'll migrate us over to Vikunja once this update to MM is merged/released.

I'm absolutely with you on the "this is everyone's problem" side of things, so any changes that move us in that direction are definitely welcomed by me!

I'd be interested to know more about the "post to discord" thing, but I think that's probably better discussed on, well, discord? :)

Copy link

Created image with name membermatters/membermatters:untrusted-pr-feature-vikunja-integration.

Copy link

Created image with name membermatters/membermatters:untrusted-pr-feature-vikunja-integration.

@jabelone jabelone merged commit 6ba7d5a into dev Aug 11, 2024
5 checks passed
@jabelone jabelone deleted the feature/vikunja-integration branch August 11, 2024 04:06
vikunja_label_id = int(config.VIKUNJA_DEFAULT_LABEL_ID)

try:
task_body = {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you only want to create a task, you don't need to provide all fields. Here it is enough to provide title and description

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for that @kolaente! I had a couple issues implementing it from the docs as it wasn't super clear what was necessary (not a complaint, your docs are way better than ours!) so I ended up inspecting the browser request and copied it's payload.

Out of interest how did you find this random PR? 😂

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also while you're here, is there a way of adding a tag during the initial task creation request or does it have to be added after the task is created?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of interest how did you find this random PR? 😂

Someone in the Vikunja forum mentioned the MemberMatters integration and so I wanted to take a look at what that is. Because of the lack of docs about it (which makes sense since the feature seems pretty new), I ended up here 😅

Also while you're here, is there a way of adding a tag during the initial task creation request or does it have to be added after the task is created?

Currently there's no way to do that. PRs welcome!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Someone in the Vikunja forum mentioned the MemberMatters integration and so I wanted to take a look at what that is.

That would be me... 😅

I'm hoping to find time in the near future to update the docs for MM around all this, we'll see if life gets in the way or not! 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants